Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1222

reference
668-tree-1
name
1222
tree-preservation-order

undefined

668-tpo-1
uprn
address-text
point
POINT (-1.014844 50.882209)
geometry
MULTIPOLYGON (((-1.014787 50.882203,-1.014790 50.882214,-1.014798 50.882224,-1.014810 50.882232,-1.014826 50.882238,-1.014843 50.882239,-1.014861 50.882238,-1.014877 50.882233,-1.014890 50.882225,-1.014898 50.882215,-1.014901 50.882204,-1.014898 50.882193,-1.014891 50.882183,-1.014878 50.882175,-1.014862 50.882169,-1.014845 50.882168,-1.014827 50.882169,-1.014811 50.882174,-1.014799 50.882182,-1.014790 50.882192,-1.014787 50.882203)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL